Three-dimensional data storage method, three-dimensional data acquisition method, three-dimensional data storage device, and three-dimensional data acquisition device

ABSTRACT

A three-dimensional data storage method includes: acquiring one or more units in which an encoded stream generated by encoding point cloud data is stored; and storing the one or more units into a file. The storing includes storing, in control information for the file, information indicating that data stored in the file is data generated by encoding the point cloud data.

BACKGROUND 1. Technical Field

The present disclosure relates to a three-dimensional data storage method, a three-dimensional data acquisition method, a three-dimensional data storage device, and a three-dimensional data acquisition device.

2. Description of the Related Art

Devices or services utilizing three-dimensional data are expected to find their widespread use in a wide range of fields, such as computer vision that enables autonomous operations of cars or robots, map information, monitoring, infrastructure inspection, and video distribution. Three-dimensional data is obtained through various means including a distance sensor such as a rangefinder, as well as a stereo camera and a combination of a plurality of monocular cameras.

Methods of representing three-dimensional data include a method known as a point cloud scheme that represents the shape of a three-dimensional structure by a point cloud in a three-dimensional space. In the point cloud scheme, the positions and colors of a point cloud are stored. While point cloud is expected to be a mainstream method of representing three-dimensional data, a massive amount of data of a point cloud necessitates compression of the amount of three-dimensional data by encoding for accumulation and transmission, as in the case of a two-dimensional moving picture (examples include Moving Picture Experts Group-4 Advanced Video Coding (MPEG-4 AVC) and High Efficiency Video Coding (HEVC) standardized by MPEG).

Meanwhile, point cloud compression is partially supported by, for example, an open-source library (Point Cloud Library) for point cloud-related processing.

Furthermore, a technique for searching for and displaying a facility located in the surroundings of the vehicle by using three-dimensional map data is known (for example, see International Publication WO 2014/020663).

SUMMARY

There has been a demand for reducing a processing amount or increasing a processing speed in devices processing three-dimensional data.

The present disclosure has an object to provide a three-dimensional data storage method, a three-dimensional data acquisition method, a three-dimensional data storage device, or a three-dimensional data acquisition device that allows a three-dimensional data processing device to reduce a processing amount or increase a processing speed.

In accordance with an aspect of the present disclosure, a three-dimensional data storage method includes: acquiring one or more units in which an encoded stream generated by encoding point cloud data is stored; and storing the one or more units into a file, wherein the storing includes storing information in control information (signaling information) for the file, the information indicating that data stored in the file is data generated by encoding the point cloud data.

In accordance with an aspect of the present disclosure, a three-dimensional data acquisition method includes: acquiring a file storing one or more units in which an encoded stream generated by encoding point cloud data is stored; and acquiring the one or more units from the file, wherein control information for the file includes information indicating that data stored in the file is data generated by encoding the point cloud data.

The present disclosure provides a three-dimensional data storage method, a three-dimensional data acquisition method, a three-dimensional data storage device, or a three-dimensional data acquisition device that allows a three-dimensional data processing device to reduce a processing amount or increase a processing speed.

BRIEF DESCRIPTION OF DRAWINGS

These and other objects, advantages and features of the disclosure will become apparent from the following description thereof taken in conjunction with the accompanying drawings that illustrate a specific embodiment of the present disclosure.

FIG. 1 is a diagram illustrating a configuration of a three-dimensional data encoding and decoding system according to Embodiment 1;

FIG. 2 is a diagram illustrating a structure example of point cloud data according to Embodiment 1;

FIG. 3 is a diagram illustrating a structure example of a data file indicating the point cloud data according to Embodiment 1;

FIG. 4 is a diagram illustrating types of the point cloud data according to Embodiment 1;

FIG. 5 is a diagram illustrating a structure of a first encoder according to Embodiment 1;

FIG. 6 is a block diagram illustrating the first encoder according to Embodiment 1;

FIG. 7 is a diagram illustrating a structure of a first decoder according to Embodiment 1;

FIG. 8 is a block diagram illustrating the first decoder according to Embodiment 1;

FIG. 9 is a diagram illustrating a structure of a second encoder according to Embodiment 1;

FIG. 10 is a block diagram illustrating the second encoder according to Embodiment 1;

FIG. 11 is a diagram illustrating a structure of a second decoder according to Embodiment 1;

FIG. 12 is a block diagram illustrating the second decoder according to Embodiment 1;

FIG. 13 is a diagram illustrating a protocol stack related to PCC encoded data according to Embodiment 1;

FIG. 14 is a diagram illustrating the protocol stack according to Embodiment 1;

FIG. 15 is a diagram illustrating a syntax example of a NAL unit according to Embodiment 1;

FIG. 16 is a diagram illustrating a syntax example of a NAL unit header according to Embodiment 1;

FIG. 17 is a diagram illustrating a semantics example of pcc_codec_type according to Embodiment 1;

FIG. 18 is a diagram illustrating a semantics example of pcc_nal_unit_type according to Embodiment 1;

FIG. 19 is a flowchart of encoding processing according to Embodiment 1;

FIG. 20 is a flowchart of decoding processing by the second decoder according to Embodiment 1;

FIG. 21 is a flowchart of decoding processing by the first decoder according to Embodiment 1;

FIG. 22 is a diagram illustrating a protocol stack according to Embodiment 2;

FIG. 23 is a diagram illustrating a syntax example of a NAL unit for codec 2 according to Embodiment 2;

FIG. 24 is a diagram illustrating a syntax example of a NAL unit header for codec 2 according to Embodiment 2;

FIG. 25 is a diagram illustrating a semantics example of codec1_nal_unit_type according to Embodiment 2;

FIG. 26 is a diagram illustrating a syntax example of a NAL unit for codec 1 according to Embodiment 2;

FIG. 27 is a diagram illustrating a syntax example of a NAL unit header for codec 1 according to Embodiment 2;

FIG. 28 is a diagram illustrating a semantics example of codec1_nal_unit_type according to Embodiment 2;

FIG. 29 is a flowchart of encoding processing according to Embodiment 2;

FIG. 30 is a flowchart of decoding processing according to Embodiment 2;

FIG. 31 is a diagram illustrating a protocol stack according to Embodiment 3;

FIG. 32 is a diagram illustrating a syntax example of a NAL unit according to Embodiment 3;

FIG. 33 is a diagram illustrating a syntax example of a NAL unit header according to Embodiment 3;

FIG. 34 is a diagram illustrating a semantics example of pcc_nal_unit_type according to Embodiment 3;

FIG. 35 is a flowchart of encoding processing according to Embodiment 3;

FIG. 36 is a flowchart of decoding processing according to Embodiment 3;

FIG. 37 is a flowchart of encoding processing according to Variation of Embodiment;

FIG. 38 is a flowchart of decoding processing according to Variation of Embodiment;

FIG. 39 is a block diagram of an encoder according to Embodiment 4;

FIG. 40 is a block diagram of a decoder according to Embodiment 4;

FIG. 41 is a flowchart of encoding processing according to Embodiment 4;

FIG. 42 is a flowchart of decoding processing according to Embodiment 4;

FIG. 43 is a diagram illustrating a basic structure of ISOBMFF according to Embodiment 5;

FIG. 44 is a diagram illustrating a protocol stack according to Embodiment 5;

FIG. 45 is a diagram illustrating an example where a NAL unit is stored in a file for codec 1 according to Embodiment 5;

FIG. 46 is a diagram illustrating an example where a NAL unit is stored in a file for codec 2 according to Embodiment 5;

FIG. 47 is a diagram illustrating a structure of a first multiplexer according to Embodiment 5;

FIG. 48 is a diagram illustrating a structure of a first demultiplexer according to Embodiment 5;

FIG. 49 is a diagram illustrating a structure of a second multiplexer according to Embodiment 5;

FIG. 50 is a diagram illustrating a structure of a second demultiplexer according to Embodiment 5;

FIG. 51 is a flowchart of processing performed by the first multiplexer according to Embodiment 5;

FIG. 52 is a flowchart of processing performed by the second multiplexer according to Embodiment 5;

FIG. 53 is a flowchart of processing performed by the first demultiplexer and the first decoder according to Embodiment 5;

FIG. 54 is a flowchart of processing performed by the second demultiplexer and the second decoder according to Embodiment 5;

FIG. 55 is a diagram illustrating structures of an encoder and a third multiplexer according to Embodiment 6;

FIG. 56 is a diagram illustrating structures of a third demultiplexer and a decoder according to Embodiment 6;

FIG. 57 is a flowchart of processing performed by the third multiplexer according to Embodiment 6;

FIG. 58 is a flowchart of processing performed by the third demultiplexer and the decoder according to Embodiment 6;

FIG. 59 is a flowchart of processing performed by a three-dimensional data storage device according to Embodiment 6; and

FIG. 60 is a flowchart of processing performed by a three-dimensional data acquisition device according to Embodiment 6.

DETAILED DESCRIPTION OF THE EMBODIMENTS

In accordance with an aspect of the present disclosure, a three-dimensional data storage method includes: acquiring one or more units in which an encoded stream generated by encoding point cloud data is stored; and storing the one or more units into a file, wherein the storing includes storing information in control information for the file, the information indicating that data stored in the file is data generated by encoding the point cloud data.

The three-dimensional data storage method allows a device that processes a file generated by the method to early determine, with reference to control information for the file, whether or not data stored in the file is encoded data of point cloud data. It is therefore possible to reduce a processing amount or increase a processing speed of the device.

For example, it is possible that the information further indicates an encoding method used in the encoding of the point cloud data out of a first encoding method and a second encoding method.

The three-dimensional data storage method allows a device that processes a file generated by the method to early determine a codec used for data stored in the file, with reference to control information for the file. It is therefore possible to reduce a processing amount or increase a processing speed of the device.

For example, it is also possible that the first encoding method is a scheme for encoding geometry information representing a position of the point cloud data by an N-ary tree, and encoding attribute information with reference to the geometry information, where N is an integer equal to or greater than 2, and the second encoding method is a scheme for generating a two-dimensional image from the point cloud data, and encoding the two-dimensional image using a video encoding method.

For example, it is further possible that the file is in conformity with ISO Based Media File Format (ISOBMFF).

In accordance with another aspect of the present disclosure, a three-dimensional data acquisition method includes: acquiring a file storing one or more units in which an encoded stream generated by encoding point cloud data is stored; and acquiring the one or more units from the file, wherein control information for the file includes information indicating that data stored in the file is data generated by encoding the point cloud data.

The three-dimensional data acquisition method makes it possible to early determine whether or not data stored in a file is encoded data of point cloud data. It is therefore possible to reduce a processing amount or increase a processing speed of a device performing the method or devices in the subsequent stages.

For example, it is possible that the information further indicates an encoding method used in the encoding of the point cloud data out of a first encoding method and a second encoding method.

The three-dimensional data acquisition method makes it possible to early determine a codec used for data stored in the file, with reference to control information for the file. It is therefore possible to reduce a processing amount or increase a processing speed of a device performing the method or devices in the subsequent stages.

For example, it is also possible that the three-dimensional data acquisition method further includes: acquiring, with reference to the information, one of data encoded by the first encoding method and data encoded using the second encoding method from the point cloud data that is encoded. For example, it is further possible that the first encoding method is a scheme for encoding geometry information representing a position of the point cloud data by an N-ary tree, and encoding attribute information with reference to the geometry information, where N is an integer equal to or greater than 2, and that the second encoding method is a scheme for generating a two-dimensional image from the point cloud data, and encoding the two-dimensional image using a video encoding method.

For example, it is further possible that the file is in conformity with ISOBMFF.

In accordance with still another aspect of the present disclosure, a three-dimensional data storage device, comprising: a processor; and memory, wherein, using the memory, the processor: acquires one or more units in which an encoded stream generated by encoding point cloud data is stored; and stores the one or more units into a file, wherein the storing includes storing information in control information for the file, the information indicating that data stored in the file is data generated by encoding the point cloud data.

The three-dimensional data storage device allows a device that processes a file generated by the three-dimensional data storage method to early determine, with reference to control information for the file, whether or not data stored in the file is encoded data of point cloud data. It is therefore possible to reduce a processing amount or increase a processing speed of the device processing the file.

In accordance with still another aspect of the present disclosure, a three-dimensional data acquisition device includes: a processor; and memory, wherein, using the memory, the processor: acquires a file storing one or more units in which an encoded stream generated by encoding point cloud data is stored; and acquires the one or more units from the file, wherein control information for the file includes information indicating that data stored in the file is data generated by encoding the point cloud data.

The three-dimensional data acquisition device makes it possible to early determine whether or not data stored in a file is encoded data of point cloud data. It is therefore possible to reduce a processing amount or increase a processing speed of three-dimensional data acquisition device or devices in the subsequent stages.

Note that these general or specific aspects may be implemented as a system, a method, an integrated circuit, a computer program, or a computer-readable recording medium such as a Compact Disc Read Only Memory (CD-ROM), or may be implemented as any combination of a system, a method, an integrated circuit, a computer program, and a recording medium. The following describes embodiments with reference to the drawings.

Note that the following embodiments show exemplary embodiments of the present disclosure. The numerical values, shapes, materials, structural components, the arrangement and connection of the structural components, steps, the processing order of the steps, etc. shown in the following embodiments are mere examples, and thus are not intended to limit the present disclosure. Of the structural components described in the following embodiments, structural components not recited in any one of the independent claims that indicate the broadest concepts will be described as optional structural components.

Embodiment 1

When using encoded data of a point cloud in a device or for a service in practice, required information for the application is desirably transmitted and received in order to reduce the network bandwidth. However, conventional encoding structures for three-dimensional data have no such a function, and there is also no encoding method for such a function.

Embodiment 1 described below relates to a three-dimensional data encoding method and a three-dimensional data encoding device for encoded data of a three-dimensional point cloud that provides a function of transmitting and receiving required information for an application, a three-dimensional data decoding method and a three-dimensional data decoding device for decoding the encoded data, a three-dimensional data multiplexing method for multiplexing the encoded data, and a three-dimensional data transmission method for transmitting the encoded data.

In particular, at present, a first encoding method and a second encoding method are under investigation as encoding methods (encoding schemes) for point cloud data. However, there is no method defined for storing the configuration of encoded data and the encoded data in a system format. Thus, there is a problem that an encoder cannot perform an MUX process (multiplexing), transmission, or accumulation of data.

In addition, there is no method for supporting a format that involves two codecs, the first encoding method and the second encoding method, such as Point Cloud Compression (PCC).

With regard to this embodiment, a configuration of PCC-encoded data that involves two codecs, a first encoding method and a second encoding method, and a method of storing the encoded data in a system format will be described.

A configuration of a three-dimensional data (point cloud data) encoding and decoding system according to this embodiment will be first described. FIG. 1 is a diagram showing an example of a configuration of the three-dimensional data encoding and decoding system according to this embodiment. As shown in FIG. 1 , the three-dimensional data encoding and decoding system includes three-dimensional data encoding system 4601, three-dimensional data decoding system 4602, sensor terminal 4603, and external connector 4604.

Three-dimensional data encoding system 4601 generates encoded data or multiplexed data by encoding point cloud data, which is three-dimensional data. Three-dimensional data encoding system 4601 may be a three-dimensional data encoding device implemented by a single device or a system implemented by a plurality of devices. The three-dimensional data encoding device may include a part of a plurality of processors included in three-dimensional data encoding system 4601.

Three-dimensional data encoding system 4601 includes point cloud data generation system 4611, presenter 4612, encoder 4613, multiplexer 4614, input/output unit 4615, and controller 4616. Point cloud data generation system 4611 includes sensor information obtainer 4617, and point cloud data generator 4618.

Sensor information obtainer 4617 obtains sensor information from sensor terminal 4603, and outputs the sensor information to point cloud data generator 4618. Point cloud data generator 4618 generates point cloud data from the sensor information, and outputs the point cloud data to encoder 4613.

Presenter 4612 presents the sensor information or point cloud data to a user. For example, presenter 4612 displays information or an image based on the sensor information or point cloud data.

Encoder 4613 encodes (compresses) the point cloud data, and outputs the resulting encoded data, control information (signaling information) obtained in the course of the encoding, and other additional information to multiplexer 4614. The additional information includes the sensor information, for example.

Multiplexer 4614 generates multiplexed data by multiplexing the encoded data, the control information, and the additional information input thereto from encoder 4613. A format of the multiplexed data is a file format for accumulation or a packet format for transmission, for example.

Input/output unit 4615 (a communication unit or interface, for example) outputs the multiplexed data to the outside. Alternatively, the multiplexed data may be accumulated in an accumulator, such as an internal memory. Controller 4616 (or an application executor) controls each processor. That is, controller 4616 controls the encoding, the multiplexing, or other processing.

Note that the sensor information may be input to encoder 4613 or multiplexer 4614. Alternatively, input/output unit 4615 may output the point cloud data or encoded data to the outside as it is.

A transmission signal (multiplexed data) output from three-dimensional data encoding system 4601 is input to three-dimensional data decoding system 4602 via external connector 4604.

Three-dimensional data decoding system 4602 generates point cloud data, which is three-dimensional data, by decoding the encoded data or multiplexed data. Note that three-dimensional data decoding system 4602 may be a three-dimensional data decoding device implemented by a single device or a system implemented by a plurality of devices. The three-dimensional data decoding device may include a part of a plurality of processors included in three-dimensional data decoding system 4602.

Three-dimensional data decoding system 4602 includes sensor information obtainer 4621, input/output unit 4622, demultiplexer 4623, decoder 4624, presenter 4625, user interface 4626, and controller 4627.

Sensor information obtainer 4621 obtains sensor information from sensor terminal 4603.

Input/output unit 4622 obtains the transmission signal, decodes the transmission signal into the multiplexed data (file format or packet), and outputs the multiplexed data to demultiplexer 4623.

Demultiplexer 4623 obtains the encoded data, the control information, and the additional information from the multiplexed data, and outputs the encoded data, the control information, and the additional information to decoder 4624.

Decoder 4624 reconstructs the point cloud data by decoding the encoded data.

Presenter 4625 presents the point cloud data to a user. For example, presenter 4625 displays information or an image based on the point cloud data. User interface 4626 obtains an indication based on a manipulation by the user. Controller 4627 (or an application executor) controls each processor. That is, controller 4627 controls the demultiplexing, the decoding, the presentation, or other processing.

Note that input/output unit 4622 may obtain the point cloud data or encoded data as it is from the outside. Presenter 4625 may obtain additional information, such as sensor information, and present information based on the additional information. Presenter 4625 may perform a presentation based on an indication from a user obtained on user interface 4626.

Sensor terminal 4603 generates sensor information, which is information obtained by a sensor. Sensor terminal 4603 is a terminal provided with a sensor or a camera. For example, sensor terminal 4603 is a mobile body, such as an automobile, a flying object, such as an aircraft, a mobile terminal, or a camera.

Sensor information that can be generated by sensor terminal 4603 includes (1) the distance between sensor terminal 4603 and an object or the reflectance of the object obtained by LIDAR, a millimeter wave radar, or an infrared sensor or (2) the distance between a camera and an object or the reflectance of the object obtained by a plurality of monocular camera images or a stereo-camera image, for example. The sensor information may include the posture, orientation, gyro (angular velocity), position (GPS information or altitude), velocity, or acceleration of the sensor, for example. The sensor information may include air temperature, air pressure, air humidity, or magnetism, for example.

External connector 4604 is implemented by an integrated circuit (LSI or IC), an external accumulator, communication with a cloud server via the Internet, or broadcasting, for example.

Next, point cloud data will be described. FIG. 2 is a diagram showing a configuration of point cloud data. FIG. 3 is a diagram showing a configuration example of a data file describing information of the point cloud data.

Point cloud data includes data on a plurality of points. Data on each point includes geometry information (three-dimensional coordinates) and attribute information associated with the geometry information. A set of a plurality of such points is referred to as a point cloud. For example, a point cloud indicates a three-dimensional shape of an object.

Geometry information (position), such as three-dimensional coordinates, may be referred to as geometry. Data on each point may include attribute information (attribute) on a plurality of types of attributes. A type of attribute is color or reflectance, for example.

One piece of attribute information may be associated with one piece of geometry information, or attribute information on a plurality of different types of attributes may be associated with one piece of geometry information. Alternatively, a plurality of pieces of attribute information on the same type of attribute may be associated with one piece of geometry information.

The configuration example of a data file shown in FIG. 3 is an example in which geometry information and attribute information are associated with each other in a one-to-one relationship, and geometry information and attribute information on N points forming point cloud data are shown.

The geometry information is information on three axes, specifically, an x-axis, a y-axis, and a z-axis, for example. The attribute information is RGB color information, for example. A representative data file is ply file, for example.

Next, types of point cloud data will be described. FIG. 4 is a diagram showing types of point cloud data. As shown in FIG. 4 , point cloud data includes a static object and a dynamic object.

The static object is three-dimensional point cloud data at an arbitrary time (a time point). The dynamic object is three-dimensional point cloud data that varies with time. In the following, three-dimensional point cloud data associated with a time point will be referred to as a PCC frame or a frame.

The object may be a point cloud whose range is limited to some extent, such as ordinary video data, or may be a large point cloud whose range is not limited, such as map information.

There are point cloud data having varying densities. There may be sparse point cloud data and dense point cloud data.

In the following, each processor will be described in detail. Sensor information is obtained by various means, including a distance sensor such as LIDAR or a range finder, a stereo camera, or a combination of a plurality of monocular cameras. Point cloud data generator 4618 generates point cloud data based on the sensor information obtained by sensor information obtainer 4617. Point cloud data generator 4618 generates geometry information as point cloud data, and adds attribute information associated with the geometry information to the geometry information.

When generating geometry information or adding attribute information, point cloud data generator 4618 may process the point cloud data. For example, point cloud data generator 4618 may reduce the data amount by omitting a point cloud whose position coincides with the position of another point cloud. Point cloud data generator 4618 may also convert the geometry information (such as shifting, rotating or normalizing the position) or render the attribute information.

Note that, although FIG. 1 shows point cloud data generation system 4611 as being included in three-dimensional data encoding system 4601, point cloud data generation system 4611 may be independently provided outside three-dimensional data encoding system 4601.

Encoder 4613 generates encoded data by encoding point cloud data according to an encoding method previously defined. In general, there are the two types of encoding methods described below. One is an encoding method using geometry information, which will be referred to as a first encoding method, hereinafter. The other is an encoding method using a video codec, which will be referred to as a second encoding method, hereinafter.

Decoder 4624 decodes the encoded data into the point cloud data using the encoding method previously defined.

Multiplexer 4614 generates multiplexed data by multiplexing the encoded data in an existing multiplexing method. The generated multiplexed data is transmitted or accumulated. Multiplexer 4614 multiplexes not only the PCC-encoded data but also another medium, such as a video, an audio, subtitles, an application, or a file, or reference time information. Multiplexer 4614 may further multiplex attribute information associated with sensor information or point cloud data.

Multiplexing schemes or file formats include ISOBMFF, MPEG-DASH, which is a transmission scheme based on ISOBMFF, MMT, MPEG-2 TS Systems, or RMP, for example.

Demultiplexer 4623 extracts PCC-encoded data, other media, time information and the like from the multiplexed data.

Input/output unit 4615 transmits the multiplexed data in a method suitable for the transmission medium or accumulation medium, such as broadcasting or communication. Input/output unit 4615 may communicate with another device over the Internet or communicate with an accumulator, such as a cloud server.

As a communication protocol, http, ftp, TCP, UDP or the like is used. The pull communication scheme or the push communication scheme can be used.

A wired transmission or a wireless transmission can be used. For the wired transmission, Ethernet (registered trademark), USB, RS-232C, HDMI (registered trademark), or a coaxial cable is used, for example. For the wireless transmission, wireless LAN, Wi-Fi (registered trademark), Bluetooth (registered trademark), or a millimeter wave is used, for example.

As a broadcasting scheme, DVB-T2, DVB-S2, DVB-C2, ATSC3.0, or ISDB-S3 is used, for example.

FIG. 5 is a diagram showing a configuration of first encoder 4630, which is an example of encoder 4613 that performs encoding in the first encoding method. FIG. 6 is a block diagram showing first encoder 4630. First encoder 4630 generates encoded data (encoded stream) by encoding point cloud data in the first encoding method. First encoder 4630 includes geometry information encoder 4631, attribute information encoder 4632, additional information encoder 4633, and multiplexer 4634.

First encoder 4630 is characterized by performing encoding by keeping a three-dimensional structure in mind. First encoder 4630 is further characterized in that attribute information encoder 4632 performs encoding using information obtained from geometry information encoder 4631. The first encoding method is referred to also as geometry-based PCC (GPCC).

Point cloud data is PCC point cloud data like a PLY file or PCC point cloud data generated from sensor information, and includes geometry information (position), attribute information (attribute), and other additional information (metadata). The geometry information is input to geometry information encoder 4631, the attribute information is input to attribute information encoder 4632, and the additional information is input to additional information encoder 4633.

Geometry information encoder 4631 generates encoded geometry information (compressed geometry), which is encoded data, by encoding geometry information. For example, geometry information encoder 4631 encodes geometry information using an N-ary tree structure, such as an octree. Specifically, in the case of an octree, a current space is divided into eight nodes (subspaces), 8-bit information (occupancy code) that indicates whether each node includes a point cloud or not is generated. A node including a point cloud is further divided into eight nodes, and 8-bit information that indicates whether each of the eight nodes includes a point cloud or not is generated. This process is repeated until a predetermined level is reached or the number of the point clouds included in each node becomes equal to or less than a threshold.

Attribute information encoder 4632 generates encoded attribute information (compressed attribute), which is encoded data, by encoding attribute information using configuration information generated by geometry information encoder 4631. For example, attribute information encoder 4632 determines a reference point (reference node) that is to be referred to in encoding a current point (current node) to be processed based on the octree structure generated by geometry information encoder 4631. For example, attribute information encoder 4632 refers to a node whose parent node in the octree is the same as the parent node of the current node, of peripheral nodes or neighboring nodes. Note that the method of determining a reference relationship is not limited to this method.

The process of encoding attribute information may include at least one of a quantization process, a prediction process, and an arithmetic encoding process. In this case, “refer to” means using a reference node for calculating a predicted value of attribute information or using a state of a reference node (occupancy information that indicates whether a reference node includes a point cloud or not, for example) for determining a parameter of encoding. For example, the parameter of encoding is a quantization parameter in the quantization process or a context or the like in the arithmetic encoding.

Additional information encoder 4633 generates encoded additional information (compressed metadata), which is encoded data, by encoding compressible data of additional information.

Multiplexer 4634 generates encoded stream (compressed stream), which is encoded data, by multiplexing encoded geometry information, encoded attribute information, encoded additional information, and other additional information. The generated encoded stream is output to a processor in a system layer (not shown).

Next, first decoder 4640, which is an example of decoder 4624 that performs decoding in the first encoding method, will be described. FIG. 7 is a diagram showing a configuration of first decoder 4640. FIG. 8 is a block diagram showing first decoder 4640. First decoder 4640 generates point cloud data by decoding encoded data (encoded stream) encoded in the first encoding method in the first encoding method. First decoder 4640 includes demultiplexer 4641, geometry information decoder 4642, attribute information decoder 4643, and additional information decoder 4644.

An encoded stream (compressed stream), which is encoded data, is input to first decoder 4640 from a processor in a system layer (not shown).

Demultiplexer 4641 separates encoded geometry information (compressed geometry), encoded attribute information (compressed attribute), encoded additional information (compressed metadata), and other additional information from the encoded data.

Geometry information decoder 4642 generates geometry information by decoding the encoded geometry information. For example, geometry information decoder 4642 restores the geometry information on a point cloud represented by three-dimensional coordinates from encoded geometry information represented by an N-ary structure, such as an octree.

Attribute information decoder 4643 decodes the encoded attribute information based on configuration information generated by geometry information decoder 4642. For example, attribute information decoder 4643 determines a reference point (reference node) that is to be referred to in decoding a current point (current node) to be processed based on the octree structure generated by geometry information decoder 4642. For example, attribute information decoder 4643 refers to a node whose parent node in the octree is the same as the parent node of the current node, of peripheral nodes or neighboring nodes. Note that the method of determining a reference relationship is not limited to this method.

The process of decoding attribute information may include at least one of an inverse quantization process, a prediction process, and an arithmetic decoding process. In this case, “refer to” means using a reference node for calculating a predicted value of attribute information or using a state of a reference node (occupancy information that indicates whether a reference node includes a point cloud or not, for example) for determining a parameter of decoding. For example, the parameter of decoding is a quantization parameter in the inverse quantization process or a context or the like in the arithmetic decoding.

Additional information decoder 4644 generates additional information by decoding the encoded additional information. First decoder 4640 uses additional information required for the decoding process for the geometry information and the attribute information in the decoding, and outputs additional information required for an application to the outside.

Next, second encoder 4650, which is an example of encoder 4613 that performs encoding in the second encoding method, will be described. FIG. 9 is a diagram showing a configuration of second encoder 4650. FIG. 10 is a block diagram showing second encoder 4650.

Second encoder 4650 generates encoded data (encoded stream) by encoding point cloud data in the second encoding method. Second encoder 4650 includes additional information generator 4651, geometry image generator 4652, attribute image generator 4653, video encoder 4654, additional information encoder 4655, and multiplexer 4656.

Second encoder 4650 is characterized by generating a geometry image and an attribute image by projecting a three-dimensional structure onto a two-dimensional image, and encoding the generated geometry image and attribute image in an existing video encoding scheme. The second encoding method is referred to as video-based PCC (VPCC).

Point cloud data is PCC point cloud data like a PLY file or PCC point cloud data generated from sensor information, and includes geometry information (position), attribute information (attribute), and other additional information (metadata).

Additional information generator 4651 generates map information on a plurality of two-dimensional images by projecting a three-dimensional structure onto a two-dimensional image.

Geometry image generator 4652 generates a geometry image based on the geometry information and the map information generated by additional information generator 4651. The geometry image is a distance image in which distance (depth) is indicated as a pixel value, for example. The distance image may be an image of a plurality of point clouds viewed from one point of view (an image of a plurality of point clouds projected onto one two-dimensional plane), a plurality of images of a plurality of point clouds viewed from a plurality of points of view, or a single image integrating the plurality of images.

Attribute image generator 4653 generates an attribute image based on the attribute information and the map information generated by additional information generator 4651. The attribute image is an image in which attribute information (color (RGB), for example) is indicated as a pixel value, for example. The image may be an image of a plurality of point clouds viewed from one point of view (an image of a plurality of point clouds projected onto one two-dimensional plane), a plurality of images of a plurality of point clouds viewed from a plurality of points of view, or a single image integrating the plurality of images.

Video encoder 4654 generates an encoded geometry image (compressed geometry image) and an encoded attribute image (compressed attribute image), which are encoded data, by encoding the geometry image and the attribute image in a video encoding scheme. Note that, as the video encoding scheme, any well-known encoding method can be used. For example, the video encoding scheme is AVC or HEVC.

Additional information encoder 4655 generates encoded additional information (compressed metadata) by encoding the additional information, the map information and the like included in the point cloud data.

Multiplexer 4656 generates an encoded stream (compressed stream), which is encoded data, by multiplexing the encoded geometry image, the encoded attribute image, the encoded additional information, and other additional information. The generated encoded stream is output to a processor in a system layer (not shown).

Next, second decoder 4660, which is an example of decoder 4624 that performs decoding in the second encoding method, will be described. FIG. 11 is a diagram showing a configuration of second decoder 4660. FIG. 12 is a block diagram showing second decoder 4660. Second decoder 4660 generates point cloud data by decoding encoded data (encoded stream) encoded in the second encoding method in the second encoding method. Second decoder 4660 includes demultiplexer 4661, video decoder 4662, additional information decoder 4663, geometry information generator 4664, and attribute information generator 4665.

An encoded stream (compressed stream), which is encoded data, is input to second decoder 4660 from a processor in a system layer (not shown).

Demultiplexer 4661 separates an encoded geometry image (compressed geometry image), an encoded attribute image (compressed attribute image), an encoded additional information (compressed metadata), and other additional information from the encoded data.

Video decoder 4662 generates a geometry image and an attribute image by decoding the encoded geometry image and the encoded attribute image in a video encoding scheme. Note that, as the video encoding scheme, any well-known encoding method can be used. For example, the video encoding scheme is AVC or HEVC.

Additional information decoder 4663 generates additional information including map information or the like by decoding the encoded additional information.

Geometry information generator 4664 generates geometry information from the geometry image and the map information. Attribute information generator 4665 generates attribute information from the attribute image and the map information.

Second decoder 4660 uses additional information required for decoding in the decoding, and outputs additional information required for an application to the outside.

In the following, a problem with the PCC encoding scheme will be described. FIG. 13 is a diagram showing a protocol stack relating to PCC-encoded data. FIG. 13 shows an example in which PCC-encoded data is multiplexed with other medium data, such as a video (HEVC, for example) or an audio, and transmitted or accumulated.

A multiplexing scheme and a file format have a function of multiplexing various encoded data and transmitting or accumulating the data. To transmit or accumulate encoded data, the encoded data has to be converted into a format for the multiplexing scheme. For example, with HEVC, a technique for storing encoded data in a data structure referred to as a NAL unit and storing the NAL unit in ISOBMFF is prescribed.

At present, a first encoding method (Codec1) and a second encoding method (Codec2) are under investigation as encoding methods for point cloud data. However, there is no method defined for storing the configuration of encoded data and the encoded data in a system format. Thus, there is a problem that an encoder cannot perform an MUX process (multiplexing), transmission, or accumulation of data.

Note that, in the following, the term “encoding method” means any of the first encoding method and the second encoding method unless a particular encoding method is specified.

In the following, a way of defining a NAL unit according to this embodiment will be described. For example, with a conventional codec, such as HEVC, a NAL unit in one format is defined for one codec. However, there has been no method that supports a format that involves two codecs, that is, the first encoding method and the second encoding method, such as PCC (such a codec will be referred to as a PCC codec, hereinafter).

In this embodiment, a format that is common to the PCC codecs is defined for a NAL unit, and an identifier of a NAL unit that depends on the PCC codec is also defined. FIG. 14 is a diagram showing a protocol stack in such a case. FIGS. 15 to 17 are diagrams illustrating an example of a NAL unit format common to the codecs. FIG. 15 is a diagram showing a syntax example of a common PCC NAL unit. FIG. 16 is a diagram showing a syntax example of a common PCC NAL unit header. FIG. 17 is a diagram showing a semantics example of pcc_codec_type. FIG. 18 is a diagram showing a semantics example of pcc_nal_unit_type, and shows an example of definitions of the NAL unit type that depends on the codec.

As a NAL unit format, a NAL unit format that is common to the PCC codecs is defined. A NAL unit (pcc_nal_unit) includes a header (pcc_nal_unit_header), a payload (pcc_nal_unit_payload), and a trailing bit (trailing_bits). Regardless of the codec, that is, whether data is to be stored in the first encoding method or the second encoding method, the same format is used.

In the NAL unit header (pcc_nal_unit_header), a codec type (pcc_codec_type) and a NAL unit type (pcc_nal_unit_type) are stored. The codec type indicates whether the PCC codec of the encoded data to be stored in the NAL unit is the first encoding method or the second encoding method.

The NAL unit type indicates the type of the NAL unit that depends on the codec, and the type is defined for each codec. If the codec type is the first encoding method, the NAL unit type indicates a NAL unit type defined for the first encoding method. If the codec type is the second encoding method, the NAL unit type indicates a NAL unit type defined for the second encoding method. That is, the NAL unit type defined for the first encoding method and the NAL unit type defined for the second encoding method are associated with different meanings with the same value.

Note that, in the header, the function of the codec type may be merged with the NAL unit type. For example, a part of the information of the NAL unit type may be used to indicate the codec type.

Next, an encoding process according to this embodiment will be described. FIG. 19 is a flowchart showing an encoding process according to this embodiment. The process in the drawing is a process performed by first encoder 4630 or second encoder 4650 defined as described above. In the following, first encoder 4630 and second encoder 4650 may not be discriminated, and the encoder may be referred to as encoder 4613. The process in the drawing is mainly performed by multiplexer 4634 shown in FIG. 6 or multiplexer 4656 shown in FIG. 10 .

Note that the process in the drawing is an example in which PCC data is encoded in any one of the first encoding method and the second encoding method, and it is supposed that which PCC codec is used for the encoding is known. For example, a user, an external device or the like may specify the PCC codec to be used.

First, encoder 4613 encodes PCC data in any of the codecs, that is, the first encoding method or the second encoding method (S4601).

When the codec used is the second encoding method (if “second encoding method” in S4602), encoder 4613 sets pcc_codec_type in the NAL unit header to a value that indicates that data included in the payload of the NAL unit is data encoded in the second encoding method (S4603). Furthermore, encoder 4613 sets pcc_nal_unit_type in the NAL unit header to the identifier of the NAL unit for the second encoding method (S4604). Encoder 4613 then generates a NAL unit having the set NAL unit header and including the encoded data in the payload. Encoder 4613 then transmits the generated NAL unit (S4605).

On the other hand, when the codec used is the first encoding method (if “first encoding method” in S4602), encoder 4613 sets pcc_codec_type in the NAL unit header to a value that indicates that data included in the payload of the NAL unit is data encoded in the first encoding method (S4606). Furthermore, encoder 4613 sets pcc_nal_unit_type in the NAL unit header to the identifier of the NAL unit for the first encoding method (S4607). Encoder 4613 then generates a NAL unit having the set NAL unit header and including the encoded data in the payload. Encoder 4613 then transmits the generated NAL unit (S4605).

If the function of pcc_codec_type is included in pcc_nal_unit_type in step S4603 or S4606, encoder 4613 may set pcc_nal_unit_type to indicate whether the codec for the NAL unit is the first encoding method or the second encoding method.

Next, a decoding process by first decoder 4640 or second decoder 4660 according to this embodiment will be described. FIG. 20 is a flowchart showing a decoding process by second decoder 4660. The process in the drawing is mainly performed by demultiplexer 4661 shown in FIG. 12 .

Note that the process in the drawing is an example in which PCC data is encoded in any one of the second encoding method and the first encoding method. In this scheme, demultiplexer 4661 in second decoder 4660 can identify the codec type of the NAL unit by referring to information included in the NAL unit header. Therefore, demultiplexer 4661 can output required information to video decoder 4662 according to the codec type.

First, second decoder 4660 receives a NAL unit (S4611). For example, the NAL unit is the NAL unit generated in the process by encoder 4613 described above. That is, the header of the NAL unit includes pcc_codec_type and pcc_nal_unit_type.

Second decoder 4660 then determines whether pcc_codec_type in the NAL unit header indicates the first encoding method or the second encoding method (S4612).

When pcc_codec_type indicates the second encoding method (if “second encoding method” in S4612), second decoder 4660 determines that the data included in the payload of the NAL unit is data encoded in the second encoding method (S4613). Second decoder 4660 then identifies the data based on the determination that pcc_nal_unit_type in the NAL unit header is the identifier of the NAL unit for the second encoding method (S4614). Second decoder 4660 then decodes the PCC data in a decoding process for the second encoding method (S4615).

On the other hand, when pcc_codec_type indicates the first encoding method (if “first encoding method” in S4612), second decoder 4660 determines that the data included in the payload of the NAL unit is data encoded in the first encoding method (S4616). In this case, second decoder 4660 does not process the NAL unit (S4617).

If the function of pcc_codec_type is included in pcc_nal_unit_type in step S4612, second decoder 4660 may refer to pcc_nal_unit_type to determine whether the codec used for the data included in the NAL unit is the first encoding method or the second encoding method.

FIG. 21 is a flowchart showing a decoding process by first decoder 4640. The process in the drawing is mainly performed by demultiplexer 4641 shown in FIG. 8 .

Note that the process in the drawing is an example in which PCC data is encoded in any one of the first encoding method and the second encoding method. In this scheme, demultiplexer 4641 in first decoder 4640 can identify the codec type of the NAL unit by referring to information included in the NAL unit header. Therefore, demultiplexer 4641 can output required information to geometry information decoder 4642 and attribute information decoder 4643 according to the codec type.

First, first decoder 4640 receives a NAL unit (S4621). For example, the NAL unit is the NAL unit generated in the process by encoder 4613 described above. That is, the header of the NAL unit includes pcc_codec_type and pcc_nal_unit_type.

First decoder 4640 then determines whether pcc_codec_type in the NAL unit header indicates the first encoding method or the second encoding method (S4622).

When pcc_codec_type indicates the second encoding method (if “second encoding method” in S4622), first decoder 4640 determines that the data included in the payload of the NAL unit is data encoded in the second encoding method (S4623). In this case, first decoder 4640 does not process the NAL unit (S4624).

On the other hand, when pcc_codec_type indicates the first encoding method (if “first encoding method” in S4622), first decoder 4640 determines that the data included in the payload of the NAL unit is data encoded in the first encoding method (S4625). First decoder 4640 then identifies the data based on the determination that pcc_nal_unit_type in the NAL unit header is the identifier of the NAL unit for the first encoding method (S4626). First decoder 4640 then decodes the PCC data in a decoding process for the first encoding method (S4627).

Embodiment 2

In Embodiment 2, another way of defining a NAL unit will be described. In this embodiment, for a NAL unit, different formats are defined for different PCC codecs. Furthermore, an identifier of the NAL unit is independently defined for each PCC codec.

FIG. 22 is a diagram showing a protocol stack in this case. FIG. 23 is a diagram showing a syntax example of a NAL unit (codec2_nal_unit) for codec 2. FIG. 24 is a diagram showing a syntax example of a NAL unit header (codec2_nal_unit_header) for codec 2. FIG. 25 is a diagram showing a semantics example of codec1_nal_unit_type.

FIG. 26 is a diagram showing a syntax example of a NAL unit (codec1_nal_unit) for codec 1. FIG. 27 is a diagram showing a syntax example of a NAL unit header (codec1_nal_unit_header) for codec 1. FIG. 28 is a diagram showing a semantics example of codec1_nal_unit_type.

A NAL unit format is independently defined for each PCC codec. A NAL unit (codec1_nal_unit, codec2_nal_unit) includes a header (codec1_nal_unit_header, codec2_nal_unit_header), a payload (codec1_nal_unit_payload, codec2_nal_unit_payload), and a trailing bit (trailing_bits). The NAL unit (codec1_nal_unit) for the first encoding method and the NAL unit (codec2_nal_unit) for the second encoding method may have the same configuration or different configurations. The NAL unit for the first encoding method and the NAL unit for the second encoding method may have different sizes.

Data encoded in the first encoding method is stored in a NAL unit for the first encoding method. Data encoded in the second encoding method is stored in a NAL unit for the second encoding method.

In the NAL unit header (codec1_nal_unit_header, codec2_nal_unit_header), the NAL unit type (codec1_nal_unit_type, codec2_nal_unit_type) is stored. The NAL unit type is independent for each codec, and the type is defined for each codec. That is, in a NAL unit for the first encoding method, a NAL unit type defined for the first encoding method is described. In a NAL unit for the second encoding method, a NAL unit type defined for the second encoding method is described.

According to this scheme, the first encoding method and the second encoding method can be handled as different codecs.

Next, an encoding process according to this embodiment will be described. FIG. 29 is a flowchart showing an encoding process according to this embodiment. The process in the drawing is a process performed by first encoder 4630 or second encoder 4650 defined as described above. The process in the drawing is mainly performed by multiplexer 4634 shown in FIG. 6 or multiplexer 4656 shown in FIG. 10 .

Note that the process in the drawing is an example in which PCC data is encoded in any one of the first encoding method and the second encoding method, and it is supposed that which PCC codec is used for the encoding is known. For example, a user, an external device or the like may specify the PCC codec to be used.

First, encoder 4613 encodes PCC data in any of the codecs, that is, the first encoding method or the second encoding method (S4631).

When the codec used is the second encoding method (if “second encoding method” in S4632), encoder 4613 generates a NAL unit in the NAL unit format for the second encoding method (S4633). Encoder 4613 then sets codec1_nal_unit_type in the NAL unit header to the identifier of the NAL unit for the second encoding method (S4634). In this way, encoder 4613 generates a NAL unit having the set NAL unit header and including the encoded data in the payload. Encoder 4613 transmits the generated NAL unit (S4635).

On the other hand, when the codec used is the first encoding method (if “first encoding method” in S4632), encoder 4613 generates a NAL unit in the NAL unit format for the first encoding method (S4636). Encoder 4613 then sets codec1_nal_unit_type in the NAL unit header to the identifier of the NAL unit for the first encoding method (S4637). In this way, encoder 4613 generates a NAL unit having the set NAL unit header and including the encoded data in the payload. Encoder 4613 then transmits the generated NAL unit (S4635).

Next, a decoding process according to this embodiment will be described. FIG. 30 is a flowchart showing a decoding process according to this embodiment. The process in the drawing is a process performed by first decoder 4640 or second decoder 4660 defined as described above. In the following, first decoder 4640 and second decoder 4660 may not be discriminated, and the decoder may be referred to as decoder 4624. The process in the drawing is mainly performed by demultiplexer 4641 shown in FIG. 8 or demultiplexer 4661 shown in FIG. 12 .

Note that the process in the drawing is an example in which PCC data is encoded in any one of the first encoding method and the second encoding method, and it is supposed that which PCC codec is used for the encoding is known. For example, information indicating the codec used is included in the transmission signal, the multiplexed data, or the encoded data, and decoder 4624 determines the codec used by referring to the information. Note that decoder 4624 may determine the codec used based on a signal obtained separately from these signals.

When the codec used is the second encoding method (if “second encoding method” in S4641), decoder 4624 receives a NAL unit in the format for the second encoding method (S4642). Decoder 4624 then identifies the data using the NAL unit format for the second encoding method and codec1_nal_unit_type for the second encoding method based on the determination that the NAL unit is for the second encoding method (S4643). Decoder 4624 then decodes the PCC data in a decoding process for the second encoding method (S4644).

On the other hand, when the codec used is the first encoding method (if “first encoding method” in S4641), decoder 4624 receives a NAL unit in the format for the first encoding method (S4645). Decoder 4624 then identifies the data using the NAL unit format for the first encoding method and codec1_nal_unit_type for the first encoding method based on the determination that the NAL unit is for the first encoding method (S4646). Decoder 4624 then decodes the PCC data in a decoding process for the first encoding method (S4647).

Embodiment 3

In Embodiment 3, another way of defining a NAL unit will be described. In this embodiment, for a NAL unit, a format that is common to PCC codecs is defined. Furthermore, an identifier of the common PCC codec NAL unit is defined.

FIG. 31 is a diagram showing a protocol stack in this case. FIGS. 32 to 34 are diagrams showing an example of a common codec NAL unit format. FIG. 32 is a diagram showing a syntax example of a common PCC NAL unit. FIG. 33 is a diagram showing a syntax example of a common PCC NAL unit header. FIG. 34 is a diagram showing a semantics example of pcc_codec_type.

As a NAL unit format, a NAL unit format that is common to the PCC codecs is defined. A NAL unit (pcc_nal_unit) includes a header (pcc_nal_unit_header), a payload (pcc_nal_unit_payload), and a trailing bit (trailing_bits). Regardless of the codec, that is, whether data is to be stored in the first encoding method or the second encoding method, the same format is used.

In the NAL unit header (pcc_nal_unit_header), a NAL unit type (pcc_nal_unit_type) is stored. The NAL unit type is common to the codecs, and a type common to the codecs is defined. That is, a common NAL unit type defined is described for both a NAL unit for the first encoding method and a NAL unit for the second encoding method. In the example shown in FIG. 34 , for example, PCC DataA is encoded data in codec 1, PCC DataB is encoded data in codec 2, PCC MetaDataA is additional information in codec 1, and PCC MetaDataB is additional information in codec 2.

According to this scheme, the first encoding method and the second encoding method can be handled as the same codec.

Next, an encoding process according to this embodiment will be described. FIG. 35 is a flowchart showing an encoding process according to this embodiment. The process in the drawing is a process performed by first encoder 4630 or second encoder 4650 defined as described above. The process in the drawing is mainly performed by multiplexer 4634 shown in FIG. 6 or multiplexer 4656 shown in FIG. 10 .

Note that the process in the drawing is an example in which PCC data is encoded in any one of the first encoding method and the second encoding method, and it is supposed that which PCC codec is used for the encoding is known. For example, a user, an external device or the like may specify the PCC codec to be used.

First, encoder 4613 encodes PCC data in any of the codecs, that is, the first encoding method or the second encoding method (S4651). Encoder 4613 then generates a NAL unit in the common PCC NAL unit format (S4652).

Encoder 4613 then sets pcc_nal_unit_type in the NAL unit header to the identifier of the common PCC NAL unit (S4653). Encoder 4613 then transmits the NAL unit having the set NAL unit header and including the encoded data in the payload (S4654).

Next, a decoding process according to this embodiment will be described. FIG. 36 is a flowchart showing a decoding process according to this embodiment. The process in the drawing is a process performed by first decoder 4640 or second decoder 4660 defined as described above. The process in the drawing is mainly performed by demultiplexer 4641 shown in FIG. 8 or demultiplexer 4661 shown in FIG. 12 .

Note that the process in the drawing is an example in which PCC data is encoded in any one of the first encoding method and the second encoding method.

First, decoder 4624 determines the codec used for the encoding of the data included in the NAL unit (S4661). For example, decoder 4624 determines the codec used by referring to pcc_nal_unit_type in the NAL unit header.

When the codec used is the second encoding method (if “second encoding method” in S4661), decoder 4624 receives a NAL unit in the common PCC format (S4662). Decoder 4624 then identifies the data using the common NAL unit format and the common pcc_nal_unit_type based on the determination that the NAL unit is a common NAL unit (S4663). Decoder 4624 then decodes the PCC data in a decoding process for the second encoding method (S4664).

On the other hand, when the codec used is the first encoding method (if “first encoding method” in S4661), decoder 4624 receives a NAL unit in the common PCC format (S4665). Decoder 4624 then identifies the data using the common NAL unit format and the common pcc_nal_unit_type based on the determination that the NAL unit is a common NAL unit (S4666). Decoder 4624 then decodes the PCC data in a decoding process for the first encoding method (S4667).

In the following, variations of Embodiments 1 to 3 described above will be described. As another method for indicating the PCC codec type, any of the following methods can also be used.

In Embodiment 1, Embodiment 2, and Embodiment 3, cases where there are two codecs, that is, the first encoding method and the second encoding method, have been described. However, the methods described above can be applied to cases where there are three or more PCC codecs.

In Embodiment 1 and Embodiment 3, identification information for the PCC codec (pcc_codec_type in Embodiment 1 or pcc_nal_unit_type in Embodiment 3) is described in the NAL unit header. However, the identification information for the codec may be stored at another location.

The first encoding method and the second encoding method are not limited to the examples described above and can be any codec. For example, the first encoding method and the second encoding method may be a plurality of codecs resulting from fragmentation of GPCC or a plurality of codecs resulting from fragmentation of VPCC. For example, both the first encoding method and the second encoding method may be VPCC, but different video encoding schemes may be used in the first encoding method and the second encoding method. The video encoding scheme may be AVC or HEVC, for example. One or both of the first encoding method and the second encoding method may be an encoding method including another encoding scheme for a video, an audio, a text application, or the like.

For example, the identification information for the codec may be included in the control information (signaling information) included in the PCC-encoded stream. Here, the control information is metadata or the like, such as a parameter set or supplemental enhancement information (SEI).

FIG. 37 is a flowchart of an encoding process by encoder 4613 in this case. First, encoder 4613 encodes PCC data (S4671), and describes the identification information for the PCC codec at a predetermined location (parameter set, for example) in the encoded data (S4672). Encoder 4613 then generates a NAL unit including the encoded data, and transmits the generated NAL unit (S4673).

The identification information for the PCC codec may be defined as profile, and indicated by metadata. When the same codec is used for the whole of a sequence, a sequence parameter set may include the identification information for the PCC codec. When a different codec is used for encoding of each PCC frame, a parameter set that describes information on each frame may include the identification information for the PCC codec. For example, when a different codec is used for each piece of PCC data, such as when different codecs are used for the geometry information and the attribute information, a parameter set that describes information on each piece of data may include the identification information for the PCC codec. That is, information indicating the codec for the geometry information may be included in control information (a parameter set or the like) for the geometry information, and information indicating the codec for the attribute information may be included in control information (a parameter set or the like) for the attribute information.

Note that the identification information for the codec may be stored at any of the locations described above or may be stored at a plurality of locations. For example, the identification information for the codec may be stored in both the encoded stream and the NAL unit header. When the identification information for the codec is stored at a plurality of locations, the same information may be stored at the plurality of locations, or different information may be stored at the plurality of locations. The “different information” are information indicating GPCC or VPCC and information indicating any of a plurality of codecs resulting from fragmentation of GPCC or VPCC.

When a NAL unit includes a parameter set, demultiplexer 4641 or 4661 included in decoder 4624 can determine whether the data included in the payload of the NAL unit is data encoded in the first encoding method or data encoded in the second encoding method by analyzing what is described in the parameter set. Therefore, decoder 4624 can quickly filter a NAL unit that is not required for decoding.

FIG. 38 is a flowchart of a decoding process by decoder 4624 in this case. First, decoder 4624 receives a NAL unit (S4675), and identifies a predetermined data that describes the identification information for the PCC codec (the parameter set described above, for example) using pcc_nal_unit_type in the NAL unit header (S4676). Decoder 4624 then identifies the PCC codec indicated in the predetermined data by analyzing predetermined data (the parameter set, for example) (S4677). Decoder 4624 then decodes the encoded data using the identified PCC codec (S4678).

Although an example in which the encoded stream is stored in a NAL unit has been shown above, any unit according to a predetermined scheme can be used instead of the NAL unit.

Embodiment 4

In Embodiment 4, encoder 4670 having the functions of both first encoder 4630 and second encoder 4650 described above and decoder 4680 having the functions of both first decoder 4640 and second decoder 4660 described above will be described.

FIG. 39 is a block diagram showing encoder 4670 according to this embodiment. Encoder 4670 includes first encoder 4630 and second encoder 4650 described above and multiplexer 4671. Multiplexer 4671 multiplexes encoded data generated by first encoder 4630 and encoded data generated by second encoder 4650, and outputs the resulting encoded data.

FIG. 40 is a block diagram showing decoder 4680 according to this embodiment. Decoder 4680 includes first decoder 4640 and second decoder 4660 described above and demultiplexer 4681. Demultiplexer 4681 extracts encoded data generated using the first encoding method and encoded data generated using second encoding method from the input encoded data. Demultiplexer 4681 outputs the encoded data generated using the first encoding method to first decoder 4640, and outputs the encoded data generated using the second encoding method to second decoder 4660.

With the configuration described above, encoder 4670 can encode point cloud data by selectively using the first encoding method or the second encoding method. Decoder 4680 can decode encoded data encoded using the first encoding method, encoded data using the second encoding method, and encoded data encoded using both the first encoding method and the second encoding method.

For example, encoder 4670 may change the encoding method (between the first encoding method and the second encoding method) on a point-cloud-data basis or on a frame basis. Alternatively, encoder 4670 may change the encoding method on the basis of an encodable unit.

For example, encoder 4670 generates encoded data (encoded stream) including the identification information for the PCC codec described above with regard to Embodiment 1 or Embodiment 3.

Demultiplexer 4681 in decoder 4680 identifies data using the identification information for the PCC codec described above with regard to Embodiment 1 or Embodiment 3, for example. When the data is data encoded in the first encoding method, demultiplexer 4681 outputs the data to first decoder 4640. When the data is data encoded in the second encoding method, demultiplexer 4681 outputs the data to second decoder 4660.

Encoder 4670 may transmit, as the control information (signaling information), information indicating whether both the encoding methods are used or any one of the encoding methods is used, in addition to the identification information for the PCC codec.

Next, an encoding process according to this embodiment will be described. FIG. 41 is a flowchart showing an encoding process according to this embodiment. Using the identification information for the PCC codec described above with regard to Embodiment 1, Embodiment 2, Embodiment 3, and variations thereof allows an encoding process ready for a plurality of codecs. Note that although FIG. 41 shows an example in which the scheme according to Embodiment 1 is used, the same process can be applied to the other schemes.

First, encoder 4670 encodes PCC data in both or one of the codecs, that is, the first encoding method and the second encoding method (S4681).

When the codec used is the second encoding method (if “second encoding method” in S4682), encoder 4670 sets pcc_codec_type in the NAL unit header to a value that indicates that data included in the payload of the NAL unit is data encoded in the second encoding method (S4683). Encoder 4670 then sets pcc_nal_unit_type in the NAL unit header to the identifier of the NAL unit for the second encoding method (S4684). Encoder 4670 then generates a NAL unit having the set NAL unit header and including the encoded data in the payload. Encoder 4670 then transmits the generated NAL unit (S4685).

On the other hand, when the codec used is the first encoding method (if “first encoding method” in S4682), encoder 4670 sets pcc_codec_type in the NAL unit header to a value that indicates that data included in the payload of the NAL unit is data encoded in the first encoding method (S4686). Encoder 4670 then sets pcc_nal_unit_type in the NAL unit header to the identifier of the NAL unit for the first encoding method (S4687). Encoder 4670 then generates a NAL unit having the set NAL unit header and including the encoded data in the payload. Encoder 4670 then transmits the generated NAL unit (S4685).

Next, a decoding process according to this embodiment will be described. FIG. 42 is a flowchart showing a decoding process according to this embodiment. Using the identification information for the PCC codec described above with regard to Embodiment 1, Embodiment 2, Embodiment 3, and variations thereof allows a decoding process ready for a plurality of codecs. Note that although FIG. 42 shows an example in which the scheme according to Embodiment 1 is used, the same process can be applied to the other schemes.

First, decoder 4680 receives a NAL unit (S4691). For example, the NAL unit is the NAL unit generated in the process by encoder 4670 described above.

Decoder 4680 then determines whether pcc_codec_type in the NAL unit header indicates the first encoding method or the second encoding method (S4692).

When pcc_codec_type indicates the second encoding method (if “second encoding method” in S4692), decoder 4680 determines that the data included in the payload of the NAL unit is data encoded in the second encoding method (S4693). Decoder 4680 then identifies the data based on the determination that pcc_nal_unit_type in the NAL unit header is the identifier of the NAL unit for the second encoding method (S4694). Decoder 4680 then decodes the PCC data in a decoding process for the second encoding method (S4695).

On the other hand, when pcc_codec_type indicates the first encoding method (if “first encoding method” in S4692), decoder 4680 determines that the data included in the payload of the NAL unit is data encoded in the first encoding method (S4696). Decoder 4680 then identifies the data based on the determination that pcc_nal_unit_type in the NAL unit header is the identifier of the NAL unit for the first encoding method (S4697). Decoder 4680 then decodes the PCC data in a decoding process for the first encoding method (S4698).

As described above, the three-dimensional data encoding device according to an aspect of the present disclosure generates an encoded stream by encoding three-dimensional data (point cloud data, for example) (in S4671 in FIG. 37 , for example), and stores information indicating the encoding method used for the encoding among the first encoding method and the second encoding method (identification information for the codec, for example) in the control information (a parameter set, for example) for the encoded stream (in S4672 in FIG. 37 , for example).

With such a configuration, the three-dimensional data decoding device can determine the encoding method used for the encoding from the information stored in the control information, when decoding the encoded stream generated by the three-dimensional data encoding device. Therefore, the three-dimensional data decoding device can correctly decode the encoded stream even when a plurality of encoding methods are used.

The three-dimensional data includes geometry information, for example. In the encoding described above, the three-dimensional data encoding device encodes the geometry information. In the storage described above, the three-dimensional data encoding device stores the information indicating the encoding method used for the encoding of the geometry information among the first encoding method and the second encoding method in the control information for the geometry information.

The three-dimensional data includes geometry information and attribute information, for example. In the encoding described above, the three-dimensional data encoding device encodes the geometry information and the attribute information. In the storage described above, the three-dimensional data encoding device stores the information indicating the encoding method used for the encoding of the geometry information among the first encoding method and the second encoding method in the control information for the geometry information, and stores the information indicating the encoding method used for the encoding of the attribute information among the first encoding method and the second encoding method in the control information for the attribute information.

With such a configuration, different encoding methods can be used for the geometry information and the attribute information, and therefore, the coding efficiency can be improved.

For example, the three-dimensional data encoding method further includes storing the encoded stream in one or more units (NAL units, for example) (in S4673 in FIG. 37 , for example).

For example, as described above with reference to FIGS. 15 to 18 illustrating Embodiment 1, the unit includes information (pcc_nal_unit_type, for example) indicating the type of data included in the unit that has a format that is common to the first encoding method and the second encoding method and is independently defined for the first encoding method and the second encoding method.

For example, as described above with reference to FIGS. 23 to 28 illustrating Embodiment 2, the unit includes information (codec1_nal_unit_type or codec2_nal_unit_type, for example) indicating the type of data included in the unit that has different formats for the first encoding method and the second encoding method and is independently defined for the first encoding method and the second encoding method.

For example, as described above with reference to FIGS. 32 to 34 illustrating Embodiment 3, the unit includes information (pcc_nal_unit_type, for example) indicating the type of data included in the unit that has a format that is common to the first encoding method and the second encoding method and is commonly defined for the first encoding method and the second encoding method.

For example, the three-dimensional data encoding device includes a processor and a memory, and the processor performs the processes described above using the memory.

The three-dimensional data decoding device according to this embodiment determines the encoding method used for encoding of an encoded stream generated by encoding of three-dimensional data based on the information indicating the encoding method used for the encoding of the three-dimensional data among the first encoding method and the second encoding method (identification information for the codec, for example) included in the control information (a parameter set, for example) for the encoded stream (in S4677 in FIG. 38 , for example), and decodes the encoded stream using the determined encoding method (in S4678 in FIG. 38 , for example).

With such a configuration, the three-dimensional data decoding device can determine the encoding method used for the encoding from the information stored in the control information, when decoding the encoded stream. Therefore, the three-dimensional data decoding device can correctly decode the encoded stream even when a plurality of encoding methods are used.

The three-dimensional data includes geometry information, and the encoded stream includes encoded data of the geometry information, for example. In the determination described above, the three-dimensional data decoding device determines the encoding method used for the encoding of the geometry information based on the information indicating the encoding method used for the encoding of the geometry information among the first encoding method and the second encoding method included in the control information for the geometry information included in the encoded stream. In the decoding described above, the three-dimensional data decoding device decodes the encoded data of the geometry information using the determined encoding method used for the encoding of the geometry information.

The three-dimensional data includes geometry information and attribute information, and the encoded stream includes encoded data of the geometry information and encoded data of the attribute information, for example. In the determination described above, the three-dimensional data decoding device determines the encoding method used for the encoding of the geometry information based on the information indicating the encoding method used for the encoding of the geometry information among the first encoding method and the second encoding method included in the control information for the geometry information included in the encoded stream, and determines the encoding method used for the encoding of the attribute information based on the information indicating the encoding method used for the encoding of the attribute information among the first encoding method and the second encoding method included in the control information for the attribute information included in the encoded stream. In the decoding described above, the three-dimensional data decoding device decodes the encoded data of the geometry information using the determined encoding method used for the encoding of the geometry information, and decodes the encoded data of the attribute information using the determined encoding method used for the encoding of the attribute information.

With such a configuration, different encoding methods can be used for the geometry information and the attribute information, and therefore, the coding efficiency can be improved.

For example, the encoded stream is stored in one or more units (NAL units, for example), and the three-dimensional data decoding device further obtains the encoded stream from the one or more units.

For example, as described above with reference to FIGS. 15 to 18 illustrating Embodiment 1, the unit includes information (pcc_nal_unit_type, for example) indicating the type of data included in the unit that has a format that is common to the first encoding method and the second encoding method and is independently defined for the first encoding method and the second encoding method.

For example, as described above with reference to FIGS. 23 to 28 illustrating Embodiment 2, the unit includes information (codec1_nal_unit_type or codec1_nal_unit_type, for example) indicating the type of data included in the unit that has different formats for the first encoding method and the second encoding method and is independently defined for the first encoding method and the second encoding method.

For example, as described above with reference to FIGS. 32 to 34 illustrating Embodiment 3, the unit includes information (pcc_nal_unit_type, for example) indicating the type of data included in the unit that has a format that is common to the first encoding method and the second encoding method and is commonly defined for the first encoding method and the second encoding method.

For example, the three-dimensional data decoding device includes a processor and a memory, and the processor performs the processes described above using the memory.

Embodiment 5

In Embodiment 5, a method of storing the NAL unit described above with regard to Embodiment 1 in an ISOBMFF file will be described.

ISOBMFF is a file format standard prescribed in ISO/IEC14496-12. ISOBMFF is a standard that does not depend on any medium, and prescribes a format that allows various media, such as a video, an audio, and a text, to be multiplexed and stored.

A basic structure (file) of ISOBMFF will be described. A basic unit of ISOBMFF is a box. A box is formed by type, length, and data, and a file is a set of various types of boxes.

FIG. 43 is a diagram showing a basic structure (file) of ISOBMFF. A file in ISOBMFF includes boxes, such as ftyp that indicates the brand of the file by four-character code (4CC), moov that stores metadata, such as control information (signaling information), and mdat that stores data.

A method for storing each medium in the ISOBMFF file is separately prescribed. For example, a method of storing an AVC video or an HEVC video is prescribed in ISO/IEC14496-15. Here, it can be contemplated to expand the functionality of ISOBMFF and use ISOBMFF to accumulate or transmit PCC-encoded data. However, there has been no convention for storing PCC-encoded data in an ISOBMFF file. In this embodiment, a method of storing PCC-encoded data in an ISOBMFF file will be described.

FIG. 44 is a diagram showing a protocol stack in a case where a common PCC codec NAL unit in an ISOBMFF file. Here, the common PCC codec NAL unit described above with regard to Embodiment 1 is stored in an ISOBMFF file. Although the NAL unit is common to PCC codecs, a storage method for each codec (Carriage of Codec1, Carriage of Codec2) is desirably prescribed, since a plurality of PCC codecs are stored in the NAL unit.

Next, a method of storing a common PCC NAL unit that supports a plurality of PCC codecs in an ISOBMFF file will be described. FIG. 45 is a diagram showing an example in which a common PCC NAL unit is stored in an ISOBMFF file for the storage method for codec 1 (Carriage of Coded). FIG. 46 is a diagram showing an example in which a common PCC NAL unit is stored in an ISOBMFF file for the storage method for codec 2 (Carriage of Codec2).

Here, ftyp is information that is important for identification of the file format, and a different identifier of ftyp is defined for each codec. When PCC-encoded data encoded in the first encoding method (encoding scheme) is stored in the file, ftyp is set to pcc1. When PCC-encoded data encoded in the second encoding method is stored in the file, ftyp is set to pcc2.

Here, pcc1 indicates that PCC codec 1 (first encoding method) is used. pcc2 indicates that PCC codec2 (second encoding method) is used. That is, pcc1 and pcc2 indicate that the data is PCC (encoded three-dimensional data (point cloud data)), and indicate the PCC codec (first encoding method or second encoding method).

In the following, a method of storing a NAL unit in an ISOBMFF file will be described. The multiplexer analyzes the NAL unit header, and describes pcc1 in ftyp of ISOBMFF if pcc_codec_type=Codec1.

The multiplexer analyzes the NAL unit header, and describes pcc2 in ftyp of ISOBMFF if pcc_codec_type=Codec2.

If pcc_nal_unit_type is metadata, the multiplexer stores the NAL unit in moov or mdat in a predetermined manner, for example. If pcc_nal_unit_type is data, the multiplexer stores the NAL unit in moov or mdat in a predetermined manner, for example.

For example, the multiplexer may store the NAL unit size in the NAL unit, as with HEVC.

According to this storage method, the demultiplexer (a system layer) can determine whether the PCC-encoded data is encoded in the first encoding method or the second encoding method by analyzing ftyp included in the file. Furthermore, as described above, by determining whether the PCC-encoded data is encoded in the first encoding method or the second encoding method, the encoded data encoded in any one of the encoding methods can be extracted from the data including both the encoded data encoded in the encoding methods. Therefore, when transmitting the encoded data, the amount of data transmitted can be reduced. In addition, according to this storage method, different data (file) formats do not need to be set for the first encoding method and the second encoding method, and a common data format can be used for the first encoding method and the second encoding method.

Note that, when the identification information for the codec, such as ftyp of ISOBMFF, is indicated in the metadata of the system layer, the multiplexer can store a NAL unit without pcc_nal_unit_type in the ISOBMFF file.

Next, configurations and operations of the multiplexer of the three-dimensional data encoding system (three-dimensional data encoding device) according to this embodiment and the demultiplexer of the three-dimensional data decoding system (three-dimensional data decoding device) according to this embodiment will be described.

FIG. 47 is a diagram showing a configuration of first multiplexer 4710. First multiplexer 4710 includes file converter 4711 that generates multiplexed data (file) by storing encoded data generated by first encoder 4630 and control information (NAL unit) in an ISOBMFF file. First multiplexer 4710 is included in multiplexer 4614 shown in FIG. 1 , for example.

FIG. 48 is a diagram showing a configuration of first demultiplexer 4720. First demultiplexer 4720 includes file inverse converter 4721 that obtains encoded data and control information (NAL unit) from multiplexed data (file) and outputs the obtained encoded data and control information to first decoder 4640. First demultiplexer 4720 is included in demultiplexer 4623 shown in FIG. 1 , for example.

FIG. 49 is a diagram showing a configuration of second multiplexer 4730. Second multiplexer 4730 includes file converter 4731 that generates multiplexed data (file) by storing encoded data generated by second encoder 4650 and control information (NAL unit) in an ISOBMFF file. Second multiplexer 4730 is included in multiplexer 4614 shown in FIG. 1 , for example.

FIG. 50 is a diagram showing a configuration of second demultiplexer 4740. Second demultiplexer 4740 includes file inverse converter 4741 that obtains encoded data and control information (NAL unit) from multiplexed data (file) and outputs the obtained encoded data and control information to second decoder 4660. Second demultiplexer 4740 is included in demultiplexer 4623 shown in FIG. 1 , for example.

FIG. 51 is a flowchart showing a multiplexing process by first multiplexer 4710. First, first multiplexer 4710 analyzes pcc_codec_type in the NAL unit header, thereby determining whether the codec used is the first encoding method or the second encoding method (S4701).

When pcc_codec_type represents the second encoding method (if “second encoding method” in S4702), first multiplexer 4710 does not process the NAL unit (S4703).

On the other hand, when pcc_codec_type represents the first encoding method (if “first encoding method” in S4702), first multiplexer 4710 describes pcc1 in ftyp (S4704). That is, first multiplexer 4710 describes information indicating that data encoded in the first encoding method is stored in the file in ftyp.

First multiplexer 4710 then analyzes pcc_nal_unit_type in the NAL unit header, and stores the data in a box (moov or mdat, for example) in a predetermined manner suitable for the data type represented by pcc_nal_unit_type (S4705). First multiplexer 4710 then creates an ISOBMFF file including the ftyp described above and the box described above (S4706).

FIG. 52 is a flowchart showing a multiplexing process by second multiplexer 4730. First, second multiplexer 4730 analyzes pcc_codec_type in the NAL unit header, thereby determining whether the codec used is the first encoding method or the second encoding method (S4711).

When pcc_codec_type represents the second encoding method (if “second encoding method” in S4712), second multiplexer 4730 describes pcc2 in ftyp (S4713). That is, second multiplexer 4730 describes information indicating that data encoded in the second encoding method is stored in the file in ftyp.

Second multiplexer 4730 then analyzes pcc_nal_unit_type in the NAL unit header, and stores the data in a box (moov or mdat, for example) in a predetermined manner suitable for the data type represented by pcc_nal_unit_type (S4714). Second multiplexer 4730 then creates an ISOBMFF file including the ftyp described above and the box described above (S4715).

On the other hand, when pcc_codec_type represents the first encoding method (if “first encoding method” in S4712), second multiplexer 4730 does not process the NAL unit (S4716).

Note that the process described above is an example in which PCC data is encoded in any one of the first encoding method and the second encoding method. First multiplexer 4710 and second multiplexer 4730 store a desired NAL unit in a file by identifying the codec type of the NAL unit. Note that, when the identification information for the PCC codec is included in a location other than the NAL unit header, first multiplexer 4710 and second multiplexer 4730 may identify the codec type (first encoding method or second encoding method) based on the identification information for the PCC codec included in the location other than the NAL unit header in step S4701 or S4711.

When storing data in a file in step S4706 or S4714, first multiplexer 4710 and second multiplexer 4730 may store the data in the file after deleting pcc_nal_unit_type from the NAL unit header.

FIG. 53 is a flowchart showing a process performed by first demultiplexer 4720 and first decoder 4640. First, first demultiplexer 4720 analyzes ftyp in an ISOBMFF file (S4721). When the codec represented by ftyp is the second encoding method (pcc2) (if “second encoding method” in S4722), first demultiplexer 4720 determines that the data included in the payload of the NAL unit is data encoded in the second encoding method (S4723). First demultiplexer 4720 also transmits the result of the determination to first decoder 4640. First decoder 4640 does not process the NAL unit (S4724).

On the other hand, when the codec represented by ftyp is the first encoding method (pcc1) (if “first encoding method” in S4722), first demultiplexer 4720 determines that the data included in the payload of the NAL unit is data encoded in the first encoding method (S4725). First demultiplexer 4720 also transmits the result of the determination to first decoder 4640.

First decoder 4640 identifies the data based on the determination that pcc_nal_unit_type in the NAL unit header is the identifier of the NAL unit for the first encoding method (S4726). First decoder 4640 then decodes the PCC data using a decoding process for the first encoding method (S4727).

FIG. 54 is a flowchart showing a process performed by second demultiplexer 4740 and second decoder 4660. First, second demultiplexer 4740 analyzes ftyp in an ISOBMFF file (S4731). When the codec represented by ftyp is the second encoding method (pcc2) (if “second encoding method” in S4732), second demultiplexer 4740 determines that the data included in the payload of the NAL unit is data encoded in the second encoding method (S4733). Second demultiplexer 4740 also transmits the result of the determination to second decoder 4660.

Second decoder 4660 identifies the data based on the determination that pcc_nal_unit_type in the NAL unit header is the identifier of the NAL unit for the second encoding method (S4734). Second decoder 4660 then decodes the PCC data using a decoding process for the second encoding method (S4735).

On the other hand, when the codec represented by ftyp is the first encoding method (pcc1) (if “first encoding method” in S4732), second demultiplexer 4740 determines that the data included in the payload of the NAL unit is data encoded in the first encoding method (S4736). Second demultiplexer 4740 also transmits the result of the determination to second decoder 4660. Second decoder 4660 does not process the NAL unit (S4737).

As described above, for example, since the codec type of the NAL unit is identified in first demultiplexer 4720 or second demultiplexer 4740, the codec type can be identified in an early stage. Furthermore, a desired NAL unit can be input to first decoder 4640 or second decoder 4660, and an unwanted NAL unit can be removed. In this case, the process of first decoder 4640 or second decoder 4660 analyzing the identification information for the codec may be unnecessary. Note that a process of referring to the NAL unit type again and analyzing the identification information for the codec may be performed by first decoder 4640 or second decoder 4660.

Furthermore, if pcc_nal_unit_type is deleted from the NAL unit header by first multiplexer 4710 or second multiplexer 4730, first demultiplexer 4720 or second demultiplexer 4740 can output the NAL unit to first decoder 4640 or second decoder 4660 after adding pcc_nal_unit_type to the NAL unit.

Embodiment 6

In Embodiment 6, a multiplexer and a demultiplexer that correspond to encoder 4670 and decoder 4680 ready for a plurality of codecs described above with regard to Embodiment 4 will be described. FIG. 55 is a diagram showing configurations of encoder 4670 and third multiplexer 4750 according to this embodiment.

Encoder 4670 encodes point cloud data in both or one of the first encoding method and the second encoding method. Encoder 4670 may change the encoding method (between the first encoding method and the second encoding method) on a point-cloud-data basis or on a frame basis. Alternatively, encoder 4670 may change the encoding method on the basis of an encodable unit.

Encoder 4670 generates encoded data (encoded stream) including the identification information for the PCC codec described above with regard to Embodiments 1 to 4.

Third multiplexer 4750 includes file converter 4751. File converter 4751 converts a NAL unit output from encoder 4670 into a PCC data file. File converter 4751 analyzes the codec identification information included in the NAL unit header, and determines whether the PCC-encoded data is data encoded in the first encoding method, data encoded in the second encoding method, or data encoded in both the encoding methods. File converter 4751 describes a brand name that allows codec identification in ftyp. For example, when indicating the data is encoded in both the encoding methods, pcc3 is described in ftyp.

Note that, when encoder 4670 describes the PCC codec identification information in a location other than the NAL unit, file converter 4751 may determine the PCC codec (encoding method) based on the identification information.

FIG. 56 is a diagram showing configurations of third demultiplexer 4760 and decoder 4680 according to this embodiment.

Third demultiplexer 4760 includes file inverse converter 4761. File inverse converter 4761 analyzes ftyp included in a file, and determines whether the PCC-encoded data is data encoded in the first encoding method, data encoded in the second encoding method, or data encoded in both the encoding methods.

When the PCC-encoded data is data encoded in any one of the encoding methods, the data is input to an appropriate one of first decoder 4640 and second decoder 4660, and is not input to the other decoder. When the PCC-encoded data is data encoded in both the encoding methods, the data is input to decoder 4680 ready for both the encoding methods.

Decoder 4680 decodes the PCC-encoded data in both or one of the first encoding method and the second encoding method.

FIG. 57 is a flowchart showing a process performed by third multiplexer 4750 according to this embodiment.

First, third multiplexer 4750 analyzes pcc_codec_type in the NAL unit header, thereby determining whether the codec(s) used is the first encoding method, the second encoding method, or both the first encoding method and the second encoding method (S4741).

When the second encoding method is used (if Yes in S4742 and “second encoding method” in S4743), third multiplexer 4750 describes pcc2 in ftyp (S4744). That is, third multiplexer 4750 describes information indicating that data encoded in the second encoding method is stored in the file in ftyp.

Third multiplexer 4750 then analyzes pcc_nal_unit_type in the NAL unit header, and stores the data in a box (moov or mdat, for example) in a predetermined manner suitable for the data type represented by pcc_nal_unit_type (S4745). Third multiplexer 4750 then creates an ISOBMFF file including the ftyp described above and the box described above (S4746).

When the first encoding method is used (if Yes in S4742 and “first encoding method” in S4743), third multiplexer 4750 describes pcc1 in ftyp (S4747). That is, third multiplexer 4750 describes information indicating that data encoded in the first encoding method is stored in the file in ftyp.

Third multiplexer 4750 then analyzes pcc_nal_unit_type in the NAL unit header, and stores the data in a box (moov or mdat, for example) in a predetermined manner suitable for the data type represented by pcc_nal_unit_type (S4748). Third multiplexer 4750 then creates an ISOBMFF file including the ftyp described above and the box described above (S4746).

When both the first encoding method and the second encoding method are used (if No in S4742), third multiplexer 4750 describes pcc3 in ftyp (S4749). That is, third multiplexer 4750 describes information indicating that data encoded in both the encoding methods is stored in the file in ftyp.

Third multiplexer 4750 then analyzes pcc_nal_unit_type in the NAL unit header, and stores the data in a box (moov or mdat, for example) in a predetermined manner suitable for the data type represented by pcc_nal_unit_type (S4750). Third multiplexer 4750 then creates an ISOBMFF file including the ftyp described above and the box described above (S4746).

FIG. 58 is a flowchart showing a process performed by third demultiplexer 4760 and decoder 4680. First, third demultiplexer 4760 analyzes ftyp included in an ISOBMFF file (S4761). When the codec represented by ftyp is the second encoding method (pcc2) (if Yes in S4762 and “second encoding method” in S4763), third demultiplexer 4760 determines that the data included in the payload of the NAL unit is data encoded in the second encoding method (S4764). Third demultiplexer 4760 also transmits the result of the determination to decoder 4680.

Decoder 4680 identifies the data based on the determination that pcc_nal_unit_type in the NAL unit header is the identifier of the NAL unit for the second encoding method (S4765). Decoder 4680 then decodes the PCC data using a decoding process for the second encoding method (S4766).

When the codec represented by ftyp is the first encoding method (pcc1) (if Yes in S4762 and “first encoding method” in S4763), third demultiplexer 4760 determines that the data included in the payload of the NAL unit is data encoded in the first encoding method (S4767). Third demultiplexer 4760 also transmits the result of the determination to decoder 4680.

Decoder 4680 identifies the data based on the determination that pcc_nal_unit_type in the NAL unit header is the identifier of the NAL unit for the first encoding method (S4768). Decoder 4680 then decodes the PCC data using a decoding process for the first encoding method (S4769).

When ftyp indicates that both the encoding methods are used (pcc3) (if No in S4762), third demultiplexer 4760 determines that the data included in the payload of the NAL unit is data encoded in both the first encoding method and the second encoding method (S4770). Third demultiplexer 4760 also transmits the result of the determination to decoder 4680.

Decoder 4680 identifies the data based on the determination that pcc_nal_unit_type in the NAL unit header is the identifier of the NAL unit for the codecs described in pcc_codec_type (S4771). Decoder 4680 then decodes the PCC data using decoding processes for both the encoding methods (S4772). That is, decoder 4680 decodes the data encoded in the first encoding method using a decoding process for the first encoding method, and decodes the data encoded in the second encoding method using a decoding process for the second encoding method.

In the following, variations of this embodiment will be described. As types of brands represented by ftyp, the types described below can be indicated by the identification information. Furthermore, a combination of a plurality of the types described below can also be indicated by the identification information.

The identification information may indicate whether the original data object yet to be PCC-encoded is a point cloud whose range is limited or a large point cloud whose range is not limited, such as map information.

The identification information may indicate whether the original data yet to be PCC-encoded is a static object or a dynamic object.

As described above, the identification information may indicate whether the PCC-encoded data is data encoded in the first encoding method or data encoded in the second encoding method.

The identification information may indicate an algorithm used in the PCC encoding. Here, the “algorithm” means an encoding method that can be used in the first encoding method or the second encoding method, for example.

The identification information may indicate a differentiation between methods of storing the PCC-encoded data into an ISOBMFF file. For example, the identification information may indicate whether the storage method used is a storage method for accumulation or a storage method for real-time transmission, such as dynamic streaming.

Although the method of storing a NAL unit described in Embodiment 1 has been described in Embodiment 5, and the method of storing a NAL unit described in Embodiment 4 has been described in Embodiment 6, the same storage methods can be applied to the NAL unit described in Embodiments 2 and 3 to store the identification information for the PCC codec into an ISOBMFF file.

Although an example in which ISOBMFF is used as a file format has been described in Embodiments 5 and 6, other formats can also be used. For example, the method according to this embodiment can also be used when PCC-encoded data is stored in MPEG-2 TS Systems, MPEG-DASH, MMT, or RMP.

Although an example in which metadata, such as the identification information, is stored in ftyp has been shown above, metadata can also be stored in a location other than ftyp. For example, the metadata may be stored in moov.

As described above, a three-dimensional data storing device (or three-dimensional data multiplexing device or three-dimensional data encoding device) performs the process shown in FIG. 59 .

First, the three-dimensional data storing device (which includes first multiplexer 4710, second multiplexer 4730 or third multiplexer 4750, for example) acquires one or more units (NAL units, for example) that store an encoded stream, which is encoded point cloud data (S4781). The three-dimensional data storing device then stores the one or more units in a file (an ISOBMFF file, for example) (S4782). In the storage (S4782), the three-dimensional data storing device also stores information indicating that the data stored in the file is encoded point cloud data (pcc1, pcc2, or pcc3, for example) in the control information (ftyp, for example) (referred to also as signaling information) for the file.

With such a configuration, a device that processes the file generated by the three-dimensional data storing device can quickly determine whether the data stored in the file is encoded point cloud data or not by referring to the control information for the file. Therefore, the processing amount of the device can be reduced, or the processing speed of the device can be increased.

For example, the information indicates the encoding method used for the encoding of the point cloud data among the first encoding method and the second encoding method. Note that the fact that the data stored in the file is encoded point cloud data and the encoding method used for the encoding of the point cloud data among the first encoding method and the second encoding method may be indicated by a single piece of information or different pieces of information.

With such a configuration, a device that processes the file generated by the three-dimensional data storing device can quickly determine the codec used for the data stored in the file by referring to the control information for the file. Therefore, the processing amount of the device can be reduced, or the processing speed of the device can be increased.

For example, the first encoding method is a method (GPCC) that encodes geometry information that represents the position of point cloud data as an N-ary tree (N represents an integer equal to or greater than 2) and encodes attribute information using the geometry information, and the second encoding method is a method (VPCC) that generates a two-dimensional image from point cloud data and encodes the two-dimensional image in a video encoding method.

For example, the file described above is in conformity with ISOBMFF (ISO-based media file format).

For example, the three-dimensional data storing device includes a processor and a memory, and the processor performs the processes described above using the memory.

As described above, a three-dimensional data acquisition device (or three-dimensional data demultiplexing device or three-dimensional data decoding device) performs the process shown in FIG. 60 .

The three-dimensional data acquisition device (which includes first demultiplexer 4720, second demultiplexer 4740, or third demultiplexer 4760, for example) acquires a file (an ISOBMFF file, for example) that stores one or more units (NAL units, for example) that store an encoded stream, which is encoded point cloud data (S4791). The three-dimensional data acquisition device acquires the one or more units from the file (S4792). The control information (ftyp, for example) for the file includes information indicating that the data stored in the file is encoded point cloud data (pcc1, pcc2, or pcc3, for example).

For example, the three-dimensional data acquisition device determines whether the data stored in the file is encoded point cloud data or not by referring to the information. When the three-dimensional data acquisition device determines that the data stored in the file is encoded point cloud data, the three-dimensional data acquisition device generates point cloud data by decoding the encoded point cloud data included in the one or more units. Alternatively, when the three-dimensional data acquisition device determines that the data stored in the file is encoded point cloud data, the three-dimensional data acquisition device outputs information indicating that the data included in the one or more units is encoded point cloud data to a processor in a subsequent stage (first decoder 4640, second decoder 4660, or decoder 4680, for example) (or notifies a processor in a subsequent stage that the data included in the one or more units is encoded point cloud data).

With such a configuration, the three-dimensional data acquisition device can quickly determine whether the data stored in the file is encoded point cloud data or not by referring to the control information for the file. Therefore, the processing amount of the three-dimensional data acquisition device or a device in a subsequent stage can be reduced, or the processing speed of the three-dimensional data acquisition device or a device in a subsequent stage can be increased.

For example, the information represents the encoding method used for the encoding among the first encoding method and the second encoding method. Note that the fact that the data stored in the file is encoded point cloud data and the encoding method used for the encoding of the point cloud data among the first encoding method and the second encoding method may be indicated by a single piece of information or different pieces of information.

With such a configuration, the three-dimensional data acquisition device can quickly determine the codec used for the data stored in the file by referring to the control information for the file. Therefore, the processing amount of the three-dimensional data acquisition device or a device in a subsequent stage can be reduced, or the processing speed of the three-dimensional data acquisition device or a device in a subsequent stage can be increased.

For example, based on the information, the three-dimensional data acquisition device acquires the data encoded in any one of the first encoding method and the second encoding method from the encoded point cloud data including the data encoded in the first encoding method and the data encoded in the second encoding method.

For example, the first encoding method is a method (GPCC) that encodes geometry information that represents the position of point cloud data as an N-ary tree (N represents an integer equal to or greater than 2) and encodes attribute information using the geometry information, and the second encoding method is a method (VPCC) that generates a two-dimensional image from point cloud data and encodes the two-dimensional image in a video encoding method.

For example, the file described above is in conformity with ISOBMFF (ISO-based media file format).

For example, the three-dimensional data acquisition device includes a processor and a memory, and the processor performs the processes described above using the memory.

A three-dimensional data storage device, a three-dimensional data acquisition device, and the like according to the embodiments of the present disclosure have been described above, but the present disclosure is not limited to these embodiments.

Note that each of the processors included in the three-dimensional data storage device, the three-dimensional data acquisition device, and the like according to the above embodiments is typically implemented as a large-scale integrated (LSI) circuit, which is an integrated circuit (IC). These may take the form of individual chips, or may be partially or entirely packaged into a single chip.

Such IC is not limited to an LSI, and thus may be implemented as a dedicated circuit or a general-purpose processor. Alternatively, a field programmable gate array (FPGA) that allows for programming after the manufacture of an LSI, or a reconfigurable processor that allows for reconfiguration of the connection and the setting of circuit cells inside an LSI may be employed.

Moreover, in the above embodiments, the structural components may be implemented as dedicated hardware or may be realized by executing a software program suited to such structural components. Alternatively, the structural components may be implemented by a program executor such as a CPU or a processor reading out and executing the software program recorded in a recording medium such as a hard disk or a semiconductor memory.

The present disclosure may also be implemented as a three-dimensional data storage method, a three-dimensional data acquisition method, or the like executed by the three-dimensional data storage device, the three-dimensional data acquisition device, and the like.

Also, the divisions of the functional blocks shown in the block diagrams are mere examples, and thus a plurality of functional blocks may be implemented as a single functional block, or a single functional block may be divided into a plurality of functional blocks, or one or more functions may be moved to another functional block. Also, the functions of a plurality of functional blocks having similar functions may be processed by single hardware or software in a parallelized or time-divided manner.

Also, the processing order of executing the steps shown in the flowcharts is a mere illustration for specifically describing the present disclosure, and thus may be an order other than the shown order. Also, one or more of the steps may be executed simultaneously (in parallel) with another step.

A three-dimensional data storage device, a three-dimensional data acquisition device, and the like according to one or more aspects have been described above based on the embodiments, but the present disclosure is not limited to these embodiments. The one or more aspects may thus include forms achieved by making various modifications to the above embodiments that can be conceived by those skilled in the art, as well forms achieved by combining structural components in different embodiments, without materially departing from the spirit of the present disclosure.

INDUSTRIAL APPLICABILITY

The present disclosure is applicable to a three-dimensional data storage device and a three-dimensional data acquisition device. 

1-11. (canceled)
 12. A three-dimensional data storage method, comprising: acquiring one or more units in which an encoded information generated by encoding point cloud data is stored; and storing the one or more units into a file, wherein the file indicates an encoding method used in the encoding of the point cloud data out of a plurality of encoding methods including a first encoding method and a second encoding method, the file is in conformity with ISO Based Media File Format (ISOBMFF), when the point cloud is encoded by the first encoding method, the generated encoded information is stored in a first unit having a first format, when the point cloud is encoded by the second encoding method, the generated encoded information is stored in a second unit having a second format different from the first format, and each of the first unit and the second unit includes a header and a payload, the payload including encoded data or metadata, the header including information indicating a type of data included in the payload.
 13. The three-dimensional data storage method according to claim 12, wherein the file further indicates that data stored in the file is data generated by encoding the point cloud data.
 14. The three-dimensional data storage method according to claim 12, wherein the first encoding method is a scheme for encoding geometry information representing a position of the point cloud data by an N-ary tree, and encoding attribute information with reference to the geometry information, where N is an integer equal to or greater than 2, and the second encoding method is a scheme for generating a two-dimensional image from the point cloud data, and encoding the two-dimensional image using a video encoding method.
 15. A three-dimensional data acquisition method, comprising: acquiring a file storing one or more units in which an encoded information generated by encoding point cloud data is stored; and acquiring the one or more units from the file, wherein the file indicates an encoding method used in the encoding of the point cloud data out of a plurality of encoding methods including a first encoding method and a second encoding method, the file is in conformity with ISO Based Media File Format (ISOBMFF), when the point cloud is encoded by the first encoding method, the generated encoded information is stored in a first unit having a first format, when the point cloud is encoded by the second encoding method, the generated encoded information is stored in a second unit having a second format different from the first format, and each of the first unit and the second unit includes a header and a payload, the payload including encoded data or metadata, the header including information indicating a type of data included in the payload.
 16. The three-dimensional data acquisition method according to claim 15, wherein the file further indicates that data stored in the file is data generated by encoding the point cloud data.
 17. The three-dimensional data acquisition method according to claim 15, wherein the first encoding method is a scheme for encoding geometry information representing a position of the point cloud data by an N-ary tree, and encoding attribute information with reference to the geometry information, where N is an integer equal to or greater than 2, and the second encoding method is a scheme for generating a two-dimensional image from the point cloud data, and encoding the two-dimensional image using a video encoding method.
 18. A three-dimensional data storage device, comprising: a processor; and memory, wherein, using the memory, the processor: acquires one or more units in which an encoded information generated by encoding point cloud data is stored; and stores the one or more units into a file, wherein the file indicates an encoding method used in the encoding of the point cloud data out of a plurality of encoding methods including a first encoding method and a second encoding method, the file is in conformity with ISO Based Media File Format (ISOBMFF), when the point cloud is encoded by the first encoding method, the generated encoded information is stored in a first unit having a first format, when the point cloud is encoded by the second encoding method, the generated encoded information is stored in a second unit having a second format different from the first format, and each of the first unit and the second unit includes a header and a payload, the payload including encoded data or metadata, the header including information indicating a type of data included in the payload.
 19. A three-dimensional data acquisition device, comprising: a processor; and memory, wherein, using the memory, the processor: acquires a file storing one or more units in which an encoded information generated by encoding point cloud data is stored; and acquires the one or more units from the file, wherein the file indicates an encoding method used in the encoding of the point cloud data out of a plurality of encoding methods including a first encoding method and a second encoding method, the file is in conformity with ISO Based Media File Format (ISOBMFF), when the point cloud is encoded by the first encoding method, the generated encoded information is stored in a first unit having a first format, when the point cloud is encoded by the second encoding method, the generated encoded information is stored in a second unit having a second format different from the first format, and each of the first unit and the second unit includes a header and a payload, the payload including encoded data or metadata, the header including information indicating a type of data included in the payload. 